-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Negated scalar condition for matchers #335
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #335 +/- ##
==========================================
+ Coverage 84.61% 84.75% +0.14%
==========================================
Files 148 149 +1
Lines 7080 7152 +72
Branches 3271 3301 +30
==========================================
+ Hits 5991 6062 +71
+ Misses 411 409 -2
- Partials 678 681 +3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
BenchmarksBenchmark execution time: 2024-10-02 19:46:12 Comparing candidate commit 1416eae in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 1 metrics, 0 unstable metrics. |
888d062
to
1fe02c2
Compare
6ee2834
to
d37459d
Compare
574fc85
to
2944e23
Compare
2944e23
to
42fc3fb
Compare
This PR introduces the ability to negate certain operators, using the
!
as a prefix. The set of operators supported are the following:!match_regex
,!phrase_match
,!exact_match
,!ip_match
and!equals
. Negated operators work through the use of thescalar_negated_condition
, which operates in a similar manner to thescalar_condition
, however only producing a match if the exhaustive evaluation of the given address + key_path results in no match.Negated operators have the following restrictions:
lower_than
andgreater_than
, as their negated version can be an operator in and of itself, e.g.greater_equal
andlower_equal
.Remaining work: